-
Notifications
You must be signed in to change notification settings - Fork 538
Introduce the dataset manifest and remove layer information from the partition table #11423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Web viewer failed to build.
Note: This comment is updated whenever you push a commit. |
701aed1
to
1cd8a69
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces the dataset manifest table functionality and removes layer-specific columns from the partition table. The dataset manifest provides layer-level metadata while the partition table now focuses solely on partition-level information.
- Adds new gRPC endpoints for dataset manifest schema and scanning operations
- Refactors partition table structure to remove layer information and add partition metadata
- Implements dataset manifest provider for DataFusion integration
Reviewed Changes
Copilot reviewed 12 out of 12 changed files in this pull request and generated 3 comments.
Show a summary per file
File | Description |
---|---|
rerun_py/src/catalog/dataset_entry.rs | Adds manifest() method to expose dataset manifest as DataFusion table |
rerun_py/rerun_bindings/rerun_bindings.pyi | Python type hints for new manifest() method |
crates/store/re_server/src/store.rs | Updates partition table schema removing layer columns and adding metadata |
crates/store/re_server/src/rerun_cloud.rs | Implements placeholder gRPC handlers for dataset manifest endpoints |
crates/store/re_redap_client/src/lib.rs | Adds error variant for dataset manifest schema operations |
crates/store/re_redap_client/src/connection_client.rs | Implements client method for dataset manifest schema fetching |
crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.rs | Generated protobuf code for new dataset manifest endpoints |
crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.rs | Schema definitions and helper methods for dataset manifest responses |
crates/store/re_protos/proto/rerun/v1alpha1/cloud.proto | Protocol buffer definitions for dataset manifest endpoints |
crates/store/re_datafusion/src/partition_table.rs | Adds TODO comment for deduplication |
crates/store/re_datafusion/src/lib.rs | Exports new DatasetManifestProvider |
crates/store/re_datafusion/src/dataset_manifest.rs | Implements DatasetManifestProvider for DataFusion integration |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
crates/store/re_protos/src/v1alpha1/rerun.cloud.v1alpha1.ext.rs
Outdated
Show resolved
Hide resolved
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Related
What
Introduces gRPC endpoints and associated SDK method to access the dataset manifest table, which contains a row per layer. Also, remove most layer-related columns from the partition table.
This PR also attempts to solidify the notion that
Scan{PartitionTable|DatasetManifest}Response
is the One True Source(tm) of information on the returned dataframe's schema.The OSS server does not yet implement the dataset manifest (RR-2482).
ext
utilitiesDatasetManifest
(fromLayerTable
)update catalog?Add dataset manifest table to the catalog provider #11444